Preparing IIS
=============
1.  Unpackage Blank.PUP in "Advanced" or "Custom" mode.

2.  When the packager prompts you to name the site, rename the site from
    "BlankSite" to "CSFHeadlines"

3.  When the Packager prompts you for the name of the Virtual Directories for
    IIS, rename "BlankSite" to "CSFHeadlines" and rename "BlankSiteBizDesk" to
    "CSFHeadlinesBizDesk"

4.  Finish upackaging, accept the default settings for the remaining screens.

5.  Copy the following files into the new IIS virtual directory:

    GLOBAL.ASA
    DEFAULT.ASP
    DUMPCONTENTLIST.ASP
    TESTHEADLINESLOADER.ASP

    NOTE:  The global.asa used is actually from one of the Commerce Server 2002
           Solution Sites.  As such, it contains a lot of extraneous code that
           isn't necessarily relevant to the sample.  To locate all code
           relevant to the sample, search for the expression:
           '*** CSFHeadlines Code ***

6.  Copy the entire contents of the "pipeline" directory to a "pipeline"
    subdirectory in the IIS virtual directory.

Preparing SQL Server
====================
1.  The Site UnPackage process should have created a "CSFHeadlines_commerce"
    database in SQL Server.

2.  Open SQL Query Analyzer and run the following SQL Scripts in the order they
    are listed:

    headlines_config.sql
    sample_headlines.sql

Preparing the CSF Components
===============================
1.  This process assumes you have already followed the configuration steps
    outlined in the Commerce Server 2002 SDK Readme.  If you have not done this
    already, please do so before proceeding.  The SDK Readme can be found at:
    C:\Program Files\Microsoft Commerce Server 2002\Readme_SDK.htm

2.  Build the Visual C++ project "CSFScoreHeadlines.dsw"

3.  Build the Visual Basic project "HeadlineLoader.vbp"

Running the sample
==================
Now that everything has been configured, you should be able to browse to
http://<server>/csfheadlines/default.asp to use the sample.  You should see the
targeted headlines appear on the page, as well as debugging and tracing info
about the data processed in the pipeline, and the data stored in the cache.